Apache Apache Wss4j
5 CVEs affecting Apache Apache Wss4j. Latest disclosed: 2026-09-30. Critical: 1, High: 3.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2026-89238 | Critical | 9.1 | 2026-09-30 | WSS4J EncryptedHeader child confusion could promote an attacker-controlled plaintext element as the decrypted header, leading to incorrect confidentiality cove… |
CVE-2026-95616 | High | 7.5 | 2026-09-30 | An integer overflow in WSS4J's DER bounds check lets an oversized allocation pass validation. An unauthenticated attacker can send a SOAP message carrying an X… |
CVE-2026-92121 | High | 7.5 | 2026-09-30 | In the WSS4J streaming (StAX) code, a signature reference using the WS-Security STR-Transform leaves an internal "inside signed content" flag permanently set… |
CVE-2026-85532 | High | 7.5 | 2026-09-30 | Apache WSS4J accepted attacker-controlled derived-key lengths and offsets without adequate bounds. This could permit cryptographically weak keys or excessive C… |
CVE-2026-92899 | Medium | 4.8 | 2026-09-30 | Apache WSS4J remembers the Nonce of each UsernameToken it accepts, so a captured token cannot be reused. It stored the Nonce as raw base64 text, but authentica… |